<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>search_analyzer | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'search-analyzer.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/search-analyzer.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/search-analyzer.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/search-analyzer.html" rel="nofollow" target="_blank">../en/search-analyzer.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="mapping.html">Mapping</a></span>
»
<span class="breadcrumb-link"><a href="mapping-params.html">Mapping parameters</a></span>
»
<span class="breadcrumb-node"><code class="literal">search_analyzer</code></span>
</div>
<div class="navheader">
<span class="prev">
<a href="properties.html">« <code class="literal">properties</code></a>
</span>
<span class="next">
<a href="similarity.html"><code class="literal">similarity</code> »</a>
</span>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="search-analyzer"></a><code class="literal">search_analyzer</code><a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/mapping/params/search-analyzer.asciidoc">edit</a>
</h2>
</div></div></div>
<p>Usually, the same <a class="xref" href="analyzer.html" title="analyzer">analyzer</a> should be applied at index time and at
search time, to ensure that the terms in the query are in the same format as
the terms in the inverted index.</p>
<p>Sometimes, though, it can make sense to use a different analyzer at search
time, such as when using the  <a class="xref" href="analysis-edgengram-tokenizer.html" title="Edge n-gram tokenizer"><code class="literal">edge_ngram</code></a>
tokenizer for autocomplete.</p>
<p>By default, queries will use the <code class="literal">analyzer</code> defined in the field mapping, but
this can be overridden with the <code class="literal">search_analyzer</code> setting:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">PUT my_index
{
  "settings": {
    "analysis": {
      "filter": {
        "autocomplete_filter": {
          "type": "edge_ngram",
          "min_gram": 1,
          "max_gram": 20
        }
      },
      "analyzer": {
        "autocomplete": { <a id="CO356-1"></a><i class="conum" data-value="1"></i>
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "lowercase",
            "autocomplete_filter"
          ]
        }
      }
    }
  },
  "mappings": {
    "properties": {
      "text": {
        "type": "text",
        "analyzer": "autocomplete", <a id="CO356-2"></a><i class="conum" data-value="2"></i>
        "search_analyzer": "standard" <a id="CO356-3"></a><i class="conum" data-value="2"></i>
      }
    }
  }
}

PUT my_index/_doc/1
{
  "text": "Quick Brown Fox" <a id="CO356-4"></a><i class="conum" data-value="3"></i>
}

GET my_index/_search
{
  "query": {
    "match": {
      "text": {
        "query": "Quick Br", <a id="CO356-5"></a><i class="conum" data-value="4"></i>
        "operator": "and"
      }
    }
  }
}</pre>
</div>
<div class="console_widget" data-snippet="snippets/778.console"></div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO356-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Analysis settings to define the custom <code class="literal">autocomplete</code> analyzer.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO356-2"><i class="conum" data-value="2"></i></a><a href="#CO356-3"></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">text</code> field uses the <code class="literal">autocomplete</code> analyzer at index time, but the <code class="literal">standard</code> analyzer at search time.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO356-4"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>This field is indexed as the terms: [ <code class="literal">q</code>, <code class="literal">qu</code>, <code class="literal">qui</code>, <code class="literal">quic</code>, <code class="literal">quick</code>, <code class="literal">b</code>, <code class="literal">br</code>, <code class="literal">bro</code>, <code class="literal">brow</code>, <code class="literal">brown</code>, <code class="literal">f</code>, <code class="literal">fo</code>, <code class="literal">fox</code> ]</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO356-5"><i class="conum" data-value="4"></i></a></p>
</td>
<td align="left" valign="top">
<p>The query searches for both of these terms: [ <code class="literal">quick</code>, <code class="literal">br</code> ]</p>
</td>
</tr>
</table>
</div>
<p>See <a href="https://www.elastic.co/guide/en/elasticsearch/guide/2.x/_index_time_search_as_you_type.html" class="ulink" target="_top">Index time search-as-you-
type</a> for a full explanation of this example.</p>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>The <code class="literal">search_analyzer</code> setting can be updated on existing fields
using the <a class="xref" href="indices-put-mapping.html" title="Put mapping API">PUT mapping API</a>.</p>
</div>
</div>
</div>
<div class="navfooter">
<span class="prev">
<a href="properties.html">« <code class="literal">properties</code></a>
</span>
<span class="next">
<a href="similarity.html"><code class="literal">similarity</code> »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>